Druid v1.68

Deployment Dates

The table below lists the deployment date of Druid v1.68 across Druid Clouds. To view the Druid Releases Calendar, see Druid ChatBot Releases.

Druid Cloud Community *.community.Druidplatform.com	Druid Cloud US *.us.Druidplatform.com	Druid Cloud Australia *au.Druidplatform.com	Druid Cloud West-Europe (PROD) *.Druidplatform.com
June 09, 2022	July 07, 2022	July 07, 2022	July 07, 2022

These release notes give you a brief, high-level description of the improvements implemented to existing features.

If you have questions about your Druid tenant, please contact support@Druidai.com or your local Druid partner for more information.

What's New

• Exception handling on flow steps with input mapping. Druid introduces a new feature on flow steps with input mapping and Exception handler active, Number of input attempts, which automatically adds an Exception step that bot authors can further design to customize the way chatbots handle exceptions addressing four types of exceptions: integration errors, internal action errors, number of input attempts reached and upload unsupported file types.





For more information, see Exception handling on flow steps with input mapping.

• Druid Data Service is Druid’s data storage used to persist entity records (across all bots) created and managed within the Druid Platform. Bot authors can further use these records in NER training and in other different contexts. For example, if you have a CRM where you keep your Accounts list, you can have as well a Data Service from Druid where you can keep the account records list.

The current Druid Data Service implementation is the first step towards conversational business applications, which will enable bot authors to manage complex web views and forms.

Note:  Druid Data Service is a tenant feature available on request. If you want to activate it, get in touch with Druid Support. For more information on how to set it on your tenant, see Druid Data Service.

Druid Data Service simplifies records authoring eliminating the need for writing SQL statements or REST integrations. It provides bot authors with an out of the box connector that allows them to use entity records within conversations without defining connection strings. For more information, see Druid Data Service Connector.

• This release introduces new entity system fields on entity / entity field creation/edit: Id, CreatedByUserId, CreatedOn, ModifiedByUserId, ModifiedOn and OperatedByBotId. For more information, see System Entity Fields.
• A new field is available on entity editing and entity field creation, Display Name that allows bot authors to localize entity records (on entity edit or entity field creation/edit) when using Druid Data Service in conversations.

Improvements

• Adaptive Cards. This release enables bot authors to design adaptive cards with input text on buttons to further design the conversation based on user input. This is especially useful when adaptive cards have multiple buttons and you want the conversation to continue differently based on which button the user clicks.





For more information, see Adaptive Card Steps.

• For an improved authoring experience, after creating a new solution, it becomes the working solution; there is no need for bot authors to select it from the Solution drop-down.
• The advanced metadata on flow steps has a new property for steps of type message with repeater, "pageSize" which by default is set to 10. This property sets the pagination of items in a collection on a flow step of type message.
Note:   The "pageSize":10 property does not automatically apply to message steps created in previous Druid versions, which took the property from choice steps; however if you save such a step, the property is added and you need to manually change its value if needed.

Bug Fixes

• Viber channel: Hero cards with more than 10 buttons were not working. In addition, at authoring time if buttons were not populated with “Value”, an error occurred and the buttons were not rendered.